🦋 Changeset detected

Latest commit: 78299e9

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Open in StackBlitz

npm i https://pkg.pr.new/@varlock/ci-env-info@585

npm i https://pkg.pr.new/varlock@585

npm i https://pkg.pr.new/@varlock/1password-plugin@585

npm i https://pkg.pr.new/@varlock/bitwarden-plugin@585

commit: 78299e9

@copilot - fix linting errors

@copilot - fix linting errors

Fixed in 8bb972d — moved processBwCliError before its call site in bw-pm-cli-helper.ts to satisfy the no-use-before-define rule.

@copilot - update the docs page too

@copilot - update the docs page too

Done in efa0a66. The docs page now covers both integrations side-by-side: a comparison table at the top, a full Password Manager / Vaultwarden section (prerequisites, Vaultwarden setup, auth steps, loading items, multiple instances), and the updated Reference section with @initBwp(), bwp(), and bwSessionToken.

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Ok this works but its awkward because you have to log in, then manually store the session token in your .env.local

I think I'll leave this in draft until we get the cache stuff merged. Then we can add a new bwpLogin() function which will let the user log in, and then cache the token.

Ok this works but its awkward because you have to log in, then manually store the session token in your .env.local

I think I'll leave this in draft until we get the cache stuff merged. Then we can add a new bwpLogin() function which will let the user log in, and then cache the token.

Storing the session token in an .env or an .env.local is indeed awkward and an anti-pattern, especially since the token never expires. The session token is only expired if one runs bw lock or bw logout.

I do something similar for combining ansible-vault to Bitwarden where I have a simple wrapper that caches the session token in the shell memory (in RAM) instead of a .env file. See: ansible-vault-bitwarden

Another (and more) interesting approach is bitwarden-cli-bio, which is a wrapper bringing biometric unlock to bw.

I would be very happy to change all my variables workflows to varlock + bw. Anything that can be done to help push this?

Thanks for posting this. I think with the addition of caching (which I’ll be merging in the next few days) you’ll have a nice DX with biometric unlock. But definitely helpful to see another implementation.